I design the quiet parts of software
I'm a product designer working on tools people open every day — finance apps, listening apps, the software that should fade into routine. Most of my work is deciding what a screen doesn't need.
I started out writing, and it never left the process: I draft every flow as prose before I draw it. If the sentence is confusing, the screen will be too — and sentences are cheaper to fix.
Away from the desk I shoot film, keep too many notebooks, and read the kind of magazines that arrive twice a year. All of it feeds back into the work eventually.
What I'm into right now
- Type systems
- Interface copy
- Film photography
- Slow software
- Fountain pens
- Morning pages
- City walks
- Pour-over coffee
- Independent magazines
- Ambient records
How I work
- Clarity first
- If a screen needs a tooltip to explain itself, the screen is the bug. I'd rather cut a feature than caption it.
- Words are design
- I write the interface before I draw it. Most flow problems are sentence problems, and sentences are cheaper to fix.
- Calm by default
- Attention is borrowed, not owned. Nothing on my screens moves, counts, or glows unless it earns the interruption.
- Finish the details
- The empty state, the error copy, the focus ring — the parts nobody demos are the parts people live with.